Automatic payment and deposit migration

ABSTRACT

The disclosure extends to methods, systems, and computer program products for migrating automatic financial services from one institution to another institution with minimum user input required.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.61/744,398, filed Sep. 25, 2012, which is hereby incorporated byreference herein in its entirety, including but not limited to thoseportions that specifically appear hereinafter, the incorporation byreference being made with the following exception: In the event that anyportion of the above-referenced provisional application is inconsistentwith this application, this application supersedes said above-referencedprovisional application.

BACKGROUND

Automatic payments and deposits have been facilitated by financialinstitutions, entities, payees, and employers for the convenience of allinvolved. Another benefit for financial service providers is that byfacilitating automatic payments and deposits they increase the number ofinteractions with their customers. The increased interaction between thefinancial institution and its customers creates a dependentrelationship, at least in part, because setting up automatic paymentsand automatic deposits is time consuming and difficult to change.Accordingly, many customers and patrons are deterred from changingfinancial institutions because of the difficulty in changing automatedservices, such as direct deposit or bill payments. Additionally,financial institutions that provide superior customer service or thelike may experience difficulty in attracting new customers because manyof the customers already have existing automatic services, such asdirect deposit or bill payments, with financial institutions that mayprovide inferior customer service or the like.

The disclosure relates generally to automatic financial services andrelates more particularly, but not necessarily entirely, to a system forautomating the switching of automatic financial services from a firstinstitution to a second institution with minimal user input.

The features and advantages of the disclosure will be set forth in thedescription which follows, and in part will be apparent from thedescription, or may be learned by the practice of the disclosure withoutundue experimentation. The features and advantages of the disclosure maybe realized and obtained by means of computing systems, networks, andcombinations of firmware, software and hardware, particularly disclosedand enumerated in the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive implementations of the disclosure aredescribed with reference to the following figures, wherein likereference numerals refer to like parts throughout the various viewsunless otherwise specified. Advantages of the disclosure will becomebetter understood with regard to the following description andaccompanying drawings where:

FIG. 1 illustrates a computer environment and network for providingautomatic switching of automatic financial service providers inaccordance with the principles and teachings of the disclosure;

FIG. 2 illustrates a schematic representation of computer hardware andprotocols that enable the various embodiments discussed herein inaccordance with the principles and teachings of the disclosure;

FIG. 3 illustrates a method for providing automated migration ofautomated financial services from an old provider to a new providerwithin a computing environment in accordance with the principles andteachings of the disclosure;

FIG. 4 illustrates a method for providing automated migration ofautomated financial services from an old provider to a new provider withthe additional functionality of suggesting additional automatedfinancial services in accordance with the principles and teachings ofthe disclosure; and

FIG. 5 illustrates a method for migrating automatic deposits from onefinancial institution to another financial institution and the featureof suggesting additional automatic deposit services for recurringtransactions in accordance with the principles and teachings of thedisclosure.

DETAILED DESCRIPTION

The disclosure extends to methods, systems, and computer based productsthat automate the switching of automatic financial services betweenfinancial institutions with minimal required user actions. In thefollowing description of the disclosure, reference is made to theaccompanying drawings, which form a part hereof, and in which is shownby way of illustration specific implementations in which the disclosuremay be practiced. It is understood that other implementations may beutilized and structural changes may be made without departing from thescope of the disclosure.

Automatic services, such as payments (bill-pay) and deposits (directdeposit), are important services that financial institutions provide totheir customers. For simplicity and clarity, the automatic service ofbill payments will be primarily used in the embodiments of thedisclosure for purposes of streamlining the disclosure. However, it willbe appreciated that the advantages and features disclosed herein alsoapply equally to the automatic deposit services. The automatic servicesprovided by a financial institution are so important, in some cases,that customers will often select a financial institution and stay with afinancial institution because of that financial institution's automatedservices, such as bill-pay and direct deposit, and that factor is oftenchosen or selected over many other factors. A common problem related toautomated services, such as bill-pay or direct deposit, is that theautomated data may be stored by a third party bill-pay provider and notnecessarily by the financial institution. Accordingly, systems andmethods will be disclosed herein for automating the switching orchanging automatic financial services from one institution to another.

FIG. 1 illustrates a computer environment and network for providingautomatic switching of automatic financial service providers.Illustrated in the figure is a user 105 that is electronically connectedto financial institutions through a network 110. The financialinstitutions may comprise an old financial institution having a server122 and a new financial institution having a server 144. The oldfinancial institution server 122 may comprise old automated financialservice data that may be used to facilitate automatic payment servicesand automatic deposit services. The new financial institution server 144may comprise new automated financial service data that may be used tofacilitate automatic payment services and automatic deposit services onbehalf of the clients of the new financial institution.

A method 112 for migrating automated financial services from the oldinstitution to the new institution is illustrated in FIG. 1. Animplementation of the migration method 112 may comprise a scrapingprocess at 151 that scrapes old bill pay or direct deposit data, an autofill process at 161, and canceling process at 171. The method 112 may beenabled by computer readable instructions stored in the memory of thecomputing environment. The method 112 may be provided from a payeeand/or funder server 170, or may be provided from a terminal of the user105.

FIG. 2 illustrates a schematic representation of computer hardware andprotocols that enable the various embodiments discussed herein.Implementations of the disclosure may comprise or utilize a specialpurpose or general-purpose computer, including computer hardware, suchas, for example, one or more processors and system memory, as discussedin greater detail below. Implementations within the scope of thedisclosure may also include physical and other computer-readable mediafor carrying or storing computer-executable instructions and/or datastructures. Such computer-readable media can be any available media thatcan be accessed by a general purpose or special purpose computer system.Computer-readable media that store computer-executable instructions arecomputer storage media (devices). Computer-readable media that carrycomputer-executable instructions are transmission media. Thus, by way ofexample, and not limitation, implementations of the disclosure cancomprise at least two distinctly different kinds of computer-readablemedia: computer storage media (devices) and transmission media.

Computer storage media (devices) includes RAM, ROM, EEPROM, CD-ROM,solid state drives (“SSDs”) (e.g., based on RAM), Flash memory,phase-change memory (“PCM”), other types of memory, other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium which can be used to store desired program code means inthe form of computer-executable instructions or data structures andwhich can be accessed by a general purpose or special purpose computer.

A “network” is defined as one or more data links that enable thetransport of electronic data between computer systems and/or modulesand/or other electronic devices. When information is transferred orprovided over a network or another communications connection (eitherhardwired, wireless, or a combination of hardwired or wireless) to acomputer, the computer properly views the connection as a transmissionmedium. Transmissions media can include a network and/or data links,which can be used to carry desired program code means in the form ofcomputer-executable instructions or data structures and which can beaccessed by a general purpose or special purpose computer. Combinationsof the above should also be included within the scope ofcomputer-readable media.

Further, upon reaching various computer system components, program codemeans in the form of computer-executable instructions or data structuresthat can be transferred automatically from transmission media tocomputer storage media (devices) (or vice versa). For example,computer-executable instructions or data structures received over anetwork or data link can be buffered in RAM within a network interfacemodule (e.g., a “NIC”), and then eventually transferred to computersystem RAM and/or to less volatile computer storage media (devices) at acomputer system. RAM can also include solid state drives (SSDs or PCIxbased real time memory tiered storage, such as FusionIO). Thus, itshould be understood that computer storage media (devices) can beincluded in computer system components that also (or even primarily)utilize transmission media.

Computer-executable instructions comprise, for example, instructions anddata which, when executed at a processor, cause a general purposecomputer, special purpose computer, or special purpose processing deviceto perform a certain function or group of functions. The computerexecutable instructions may be, for example, binaries, intermediateformat instructions such as assembly language, or even source code.Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the described features or acts described above.Rather, the described features and acts are disclosed as example formsof implementing the claims.

Those skilled in the art will appreciate that the disclosure may bepracticed in network computing environments with many types of computersystem configurations, including, personal computers, desktop computers,laptop computers, message processors, hand-held devices, hand pieces,multi-processor systems, microprocessor-based or programmable consumerelectronics, network PCs, minicomputers, mainframe computers, mobiletelephones, PDAs, tablets, pagers, routers, switches, various storagedevices, and the like. It should be noted that any of the abovementioned computing devices may be provided by or located within a brickand mortar location. The disclosure may also be practiced in distributedsystem environments where local and remote computer systems, which arelinked (either by hardwired data links, wireless data links, or by acombination of hardwired and wireless data links) through a network,both perform tasks. In a distributed system environment, program modulesmay be located in both local and remote memory storage devices.

Further, where appropriate, functions described herein can be performedin one or more of: hardware, software, firmware, digital components, oranalog components. For example, one or more application specificintegrated circuits (ASICs) or field programmable gate arrays (FPGAs)can be programmed to carry out one or more of the systems and proceduresdescribed herein. It will be appreciated that certain terms are usedthroughout the description and claims to refer to particular systemcomponents. As one skilled in the art will appreciate, components may bereferred to by different names. This document does not intend todistinguish between components that differ in name, but not function.

Illustrated in FIG. 2 is a block diagram illustrating an examplecomputing device 200. Computing device 200 may be used to performvarious procedures, such as those discussed herein. Computing device 200can function as a server, a client, or any other computing entity.Computing device 200 can perform various monitoring functions asdiscussed herein, and can execute one or more application programs, suchas the application programs described herein. Computing device 200 canbe any of a wide variety of computing devices, such as a desktopcomputer, a notebook computer, a server computer, a handheld computer,tablet computer and the like.

Computing device 200 includes one or more processor(s) 202, one or morememory device(s) 204, one or more interface(s) 206, one or more massstorage device(s) 208, one or more Input/Output (I/O) device(s) 210, anda display device 230 all of which are coupled to a bus 212. Processor(s)202 include one or more processors or controllers that executeinstructions stored in memory device(s) 204 and/or mass storagedevice(s) 208. Processor(s) 202 may also include various types ofcomputer-readable media, such as cache memory.

Memory device(s) 204 include various computer-readable media, such asvolatile memory (e.g., random access memory (RAM) 214) and/ornonvolatile memory (e.g., read-only memory (ROM) 216). Memory device(s)204 may also include rewritable ROM, such as Flash memory.

Mass storage device(s) 208 include various computer readable media, suchas magnetic tapes, magnetic disks, optical disks, solid-state memory(e.g., Flash memory), and so forth. As shown in the figure, a particularmass storage device is a hard disk drive 224. Various drives may also beincluded in mass storage device(s) 208 to enable reading from and/orwriting to the various computer readable media. Mass storage device(s)208 include removable media 226 and/or non-removable media.

I/O device(s) 210 include various devices that allow data and/or otherinformation to be input to or retrieved from computing device 200.Example I/O device(s) 210 include digital cursor control devices,keyboards, keypads, microphones, monitors or other display devices,speakers, printers, network interface cards, modems, and the like.

Display device 230 includes any type of device capable of displayinginformation to one or more users of computing device 200. Examples ofdisplay device 580 include a monitor, display terminal, video projectiondevice, and the like.

Interface(s) 206 include various interfaces that allow computing device200 to interact with other systems, devices, or computing environments.Example interface(s) 206 may include any number of different networkinterfaces 220, such as interfaces to local area networks (LANs), widearea networks (WANs), wireless networks, and the Internet. Otherinterface(s) include user interface 218 and peripheral device interface222. The interface(s) 206 may also include one or more user interfaceelements 218. The interface(s) 206 may also include one or moreperipheral interfaces such as interfaces for printers, pointing devices(mice, track pad, etc.), keyboards, and the like.

Bus 212 allows processor(s) 202, memory device(s) 204, interface(s) 206,mass storage device(s) 208, and I/O device(s) 210 to communicate withone another, as well as other devices or components coupled to bus 212.Bus 212 represents one or more of several types of bus structures, suchas a system bus, PCI bus, IEEE 1394 bus, USB bus, and so forth.

For purposes of illustration, programs and other executable programcomponents are shown herein as discrete blocks, although it isunderstood that such programs and components may reside at various timesin different storage components of computing device 200, and areexecuted by processor(s) 202. Alternatively, the systems and proceduresdescribed herein can be implemented in hardware, or a combination ofhardware, software, and/or firmware. For example, one or moreapplication specific integrated circuits (ASICs) or field programmablegate arrays (FPGAs) can be programmed to carry out one or more of thesystems and procedures described herein.

Referring now to FIG. 3, there is illustrated a method for providingautomated migration of automated financial services from an old providerto a new provider within a computing environment. For example, if afinancial institution wishes to switch to a new bill-pay provider, itmay lose historical data and the users/customers may need to enter allof their bill-pay information again (accounts, payees, funders, etc.).This can cause major disruption for users and many of them will leave afinancial institution in such an instance. Therefore, from a financialinstitution's point of view, a method is needed to support financialinstitutions (and its users) when changing bill-pay providers withoutdisruption to customers or prohibitive fees being charged by thebill-pay provider to migrate or allow access to bill-pay data.Accordingly, at 310 of migration method 300 account data may be receivedfrom an aggregation source and stored in computer memory. The accountdata may comprise transaction data associate with user accounts such as;automatic bill pay, automatic deposit, payee information, amountinformation, etc.

At 320, current automated services may be determined. The determinationsmay be made by any known computer method such as, for example, patternrecognition, string matching, data tags, meta data, and the like.

At 330, once the automated services have been identified, payee andpayment information may be scraped from the automated servicestransactions. For example, an implementation may comprise the process ofscraping bill-pay information from the bill-pay provider's onlineinterfaces, or use an aggregation source to gather bill-pay information.Existing bill-pay can often be scraped, gathered by aggregators or thelike. This will allow an entity to capture some or all of the data thatthe user has in their current bill-pay setup.

At 340, the scraped payment data may be received by the new financialinstitution and stored in memory for use in setting up new automaticfinancial services. For example, when the need for switching bill-payproviders arises, potentially all of that information, includinghistorical information, as far back as the scrape, aggregators or othersources exist, will be available immediately and will be reconstructedusing the gathered data (and potentially additional user input at somesteps of the migration). This permits switching bill-pay providerswithout the users needing to set up all of their bill-pay from scratch.

At 350, forms associated with new automatic financial services may bepopulated with the payment data received and stored during process 340.

At 360, old automatic financial service may be cancelled with the oldprovider in order to prevent double payments and deposits.

Referring now to FIG. 4, there is illustrated a method for providingautomated migration of automated financial services from an old providerto a new provider with the additional functionality of suggestingadditional automatic financial services. For example, an aggregation offinancial transactions may comprise a plurality of recurring paymentsand deposits that have yet to be automated by a financial servicesprovider. In such an instance, a method for identifying thesetransactions and suggesting automatic services is needed. Accordingly,at 410 of migration method 400 account data may be received from anaggregation source and stored in computer memory. The account data maycomprise transaction data associate with user accounts, such asautomatic bill-pay, automatic deposit, payee information, amountinformation, etc. It will be appreciated that a request to transfer ormigrate at least one set of automated account data, such as bill-pay ordirect deposit data, from one financial institution to another may comedirectly from an end-user, or such a request may come from a financialinstitution without departing from the scope of the disclosure.Additionally, the account data may comprise recurring payments anddeposits that could be automated, but may or may not be set up into anautomated payment or deposit system.

At 420, current automated services may be determined. The determinationsmay be made by any known computer method such as, for example, patternrecognition, string matching, data tags, meta data, and the like.

At 430, once the automated services have been identified, payee andpayment information may be scraped from the automated servicestransactions. For example, an implementation may comprise the process ofscraping bill-pay information from the bill-pay provider's onlineinterfaces, or use an aggregation source to gather bill-pay information.Existing bill-pay can often be scraped, gathered by aggregators or thelike. This will allow an entity to capture some or all of the data thatthe user has in their current bill-pay setup.

At 440, the scraped payment data may be received by the new financialinstitution and stored in memory for use in setting up new automaticfinancial services. For example, when the need for switching bill-payproviders arises, potentially all of that information, includinghistorical information, as far back as the scrape, aggregators or othersources exist, will be available immediately and will be reconstructedusing the gathered data (and potentially additional user input at somesteps of the migration). This permits switching bill-pay providerswithout the users needing to set up all of their bill-pay from scratch.

At 450, the system may identify recurring payments and deposits that arebeing made on a regular basis. In an implementation a threshold may beestablished for identifying what qualifies as a recurring financialservice. For example, a payment that happens every month around the sameday of the month may be determined to be recurring. In the presentexample, a date range may be used as a threshold for determiningrecurrence.

At 460, an occurrence threshold may be determined. An occurrencethreshold may determine that a certain transaction must be repeated atleast a predetermined number of times to be considered recurring.

At 470, the method may suggest to the user the additional financialservices that may be automated.

At 480, new forms associated with the new and suggested automaticfinancial services may be populated with the payment data received andstored during process 440.

At 490, old automatic financial service may be cancelled with the oldprovider in order to prevent double payments and deposits.

An implementation of a method for migrating automatic bill payments froma first financial institution to a second financial institution over anetwork of computers may comprise receiving a request from a user formigrating current automatic bill payments from a first financialinstitution to a second financial institution; receiving a request froma user for aggregated account data; retrieving from an aggregationsource the desired aggregated account data comprising transaction data;determining automatic payments currently being made by the firstfinancial institution; scraping payment information for each of theautomatic payments currently being made by the first financially andstoring the payee information in computer memory; scraping payeeinformation for each of the automatic payments currently being made bythe first financially and storing the payee information in computermemory; retrieving new automatic payment forms from the second financialinstitution and populating the new automatic payment forms with thepayee and payment information retrieved from computer memory; andcanceling the current automatic payments with the first financialinstitution.

FIG. 5 illustrates a method for migrating automatic deposits from onefinancial institution to another financial institution and the featureof suggesting additional automatic deposit services for recurringtransactions. It will be appreciated that a request to transfer ormigrate at least one set of automated direct deposit data from onefinancial institution to another may come directly from an end-user, orsuch a request may come from a financial institution without departingfrom the scope of the disclosure.

At 510 of migration method 500, account data may be received from anaggregation source and stored in computer memory. The account data maycomprise deposit transaction data associated with user accounts.Additionally, the account data may comprise recurring deposits thatcould be automated for additional convenience for the user.

At 520, current automated deposit services may be determined. Thedeterminations may be made by any known computer method such as, forexample, pattern recognition, string matching, data tags, meta data, andthe like.

At 530, once the automated services have been identified, funder andfunding information may be scraped from the automated servicestransactions. For example, an implementation may comprise the process ofscraping direct deposit information from the funding provider's onlineinterfaces, or use an aggregation source to gather direct depositinformation. Existing direct deposits can often be scraped, gathered byaggregators or the like. This will allow an entity to capture some orall of the data that the user has in their current direct deposit setup.

At 540, the scraped deposit data may be received by the new financialinstitution and stored in memory for use in setting up new automaticdeposit services. For example, when the need for switching directdeposit providers arises, potentially all of that scraped information,including historical information, as far back as the scrape, aggregatorsor other sources exist, will be available immediately and will bereconstructed using the gathered data (and potentially additional userinput at some steps of the migration). This permits the switching offunding providers without the users needing to set up all of theirdirect deposits from scratch.

At 550, the system may identify deposits that are being made on aregular basis. In an implementation a threshold may be established foridentifying what qualifies as a recurring financial service. Forexample, a deposit that is made manually every month around the same dayof the month or a deposit that is about the same amount every month maybe determined to be recurring. In the present example, a date range maybe used as a threshold for determining recurrence.

At 560, an occurrence threshold may be determined. An occurrencethreshold may determine that a certain transaction must be repeated atleast a predetermined number of times to be considered recurring.

At 570, the method may suggest to the user the additional depositservices that may be automated.

At 580, new forms associated with the new and suggested automaticfinancial services may be populated with the deposit data received andstored during process at 540.

At 590, old automatic financial services may be cancelled with the oldprovider in order to prevent erroneous deposits and depositexpectations.

An implementation may provide a method for migrating automatic depositfrom a first financial institution to a second financial institutionover a network of computers and may comprise receiving request from auser for migrating current automatic deposit from a first financialinstitution to a second financial institution; receiving a request froma user for aggregated account data; retrieving from an aggregationsource the desired aggregated account data comprising transaction data;determining automatic deposits currently being made by the firstfinancial institution; scraping deposits information for each of theautomatic deposits currently being made by the first financially andstoring funder information in computer memory; scraping funderinformation for each of the automatic deposits currently being made bythe first financially and storing the funder information in computermemory; retrieving new automatic deposit forms from the second financialinstitution and populating the new automatic deposit forms with thefunder and deposit information retrieved from computer memory; andcanceling the current automatic deposits with the first financialinstitution.

Additionally, an implementation may automatically set up the accountsand payments based on the gathered data or data acquired from any thirdparty source. There may be some data missed by the source, such as somepartial account numbers or other data and the system can prompt the userfor the missing information. Because most of the data may be autofilled, users are re-entering much smaller amounts of data and themigration is much less timely and possibly even painless to theend-user, thereby facilitating an easy and successful migration withminimal inconvenience.

An implementation may use a scrape method to gather (or acquire) thedesired information and automatically set up (or partially set up)bill-pay with a new bill-pay provider.

An implementation may further comprising reformatting the request to becompatible with the aggregation source; sending the reformatted requestto the aggregation source over the network of computers; receivingrequested data from the aggregation source over the network ofcomputers; and presenting the aggregated account data to the user.

An implementation may further comprise determining if the payment amountis static and storing the payment amount in computer memory.

An implementation may further comprise searching transaction data forrecurring payments that are not automatic and scraping the recurringpayments for payee information and storing the payee information incomputer memory.

An implementation may further comprise retrieving the payee informationfrom computer memory and presenting the payee information to a user witha suggestion of converting the recurring payments to automatic paymentsmade by the second financial institution.

An implementation may further comprise determining a recurrencethreshold based in time between payments to the same payee.

An implementation may further comprise determining a recurrencethreshold based on number of times payee is represented within thetransaction data.

An implementation may comprise requests from the user that compriseslogin information for granting access to auto payment controls.

In describing and claiming the subject matter of the disclosure, thefollowing terminology will be used in accordance with the definitionsset out below.

It must be noted that, as used in this specification and the appendedclaims, the singular forms “a,” “an,” and “the” include plural referentsunless the context clearly dictates otherwise.

As used herein, “user” is intended to denote a person or entity that isutilizing the methods and the systems disclosed herein.

As used herein, the terms “comprising,” “including,” “containing,”“characterized by,” and grammatical equivalents thereof are inclusive oropen-ended terms that do not exclude additional, unrecited elements ormethod steps.

As used herein, the phrase “consisting of” and grammatical equivalentsthereof exclude any element or step not specified in the claim.

As used herein, the phrase “consisting essentially of” and grammaticalequivalents thereof limit the scope of a claim to the specifiedmaterials or steps and those that do not materially affect the basic andnovel characteristic or characteristics of the claimed disclosure.

The foregoing description has been presented for the purposes ofillustration and description. It is not intended to be exhaustive or tolimit the disclosure to the precise form disclosed. Many modificationsand variations are possible in light of the above teaching. Further, itshould be noted that any or all of the aforementioned alternateimplementations may be used in any combination desired to formadditional hybrid implementations of the disclosure.

Further, although specific implementations of the disclosure have beendescribed and illustrated, the disclosure is not to be limited to thespecific forms or arrangements of parts so described and illustrated.The scope of the disclosure is to be defined by the claims appendedhereto, any future claims submitted here and in different applications,and their equivalents.

What is claimed is:
 1. A method for migrating automatic bill paymentsfrom a first financial institution to a second financial institutionover a network of computers comprising: receiving request from a userfor migrating current automatic bill payments from a first financialinstitution to a second financial institution; receiving a request froma user for aggregated account data; retrieving from an aggregationsource the desired aggregated account data comprising transaction data;determining automatic payments currently being made by the firstfinancial institution; scraping payment information for each of theautomatic payments currently being made by the first financially andstoring the payee information in computer memory; scraping payeeinformation for each of the automatic payments currently being made bythe first financially and storing the payee information in computermemory; retrieving new automatic payment forms from the second financialinstitution and populating the new automatic payment forms with thepayee and payment information retrieved from computer memory; cancelingthe current automatic payments with the first financial institution. 2.The method of claim 1, further comprising reformatting the request to becompatible with the aggregation source; sending the reformatted requestto the aggregation source over the network of computers; receivingrequested data from the aggregation source over the network ofcomputers; presenting the aggregated account data to the user.
 3. Themethod of claim 1, further comprising determining if the payment amountis static and storing the payment amount in computer memory.
 4. Themethod of claim 1, further comprising searching transaction data forrecurring payments that are not automatic and scraping the recurringpayments for payee information and storing the payee information incomputer memory.
 5. The method of claim 4, further comprising retrievingthe payee information from computer memory and presenting the payeeinformation to a user with a suggestion of converting the recurringpayments to automatic payments made by the second financial institution.6. The method of claim 5, further comprising determining a recurrencethreshold based in time between payments to the same payee.
 7. Themethod of claim 5, further comprising determining a recurrence thresholdbased on number of times payee is represented within the transactiondata.
 8. The method of claim 1, wherein the request from the usercomprises login information for granting access to auto paymentcontrols.
 9. A method for migrating automatic deposit from a firstfinancial institution to a second financial institution over a networkof computers comprising: receiving request from a user for migratingcurrent automatic deposit from a first financial institution to a secondfinancial institution; receiving a request from a user for aggregatedaccount data; retrieving from an aggregation source the desiredaggregated account data comprising transaction data; determiningautomatic deposits currently being made by the first financialinstitution; scraping deposits information for each of the automaticdeposits currently being made by the first financially and storingfunder information in computer memory; scraping funder information foreach of the automatic deposits currently being made by the firstfinancially and storing the funder information in computer memory;retrieving new automatic deposit forms from the second financialinstitution and populating the new automatic deposit forms with thefunder and deposit information retrieved from computer memory; cancelthe current automatic deposits with the first financial institution. 10.The method of claim 9, further comprising reformatting the request to becompatible with the aggregation source; sending the reformatted requestto the aggregation source over the network of computers; receiverequested data from the aggregation source over the network ofcomputers; present the aggregated account data to the user.
 11. Themethod of claim 9, further comprising determining if the deposit amountis static and storing the deposit amount in computer memory.
 12. Themethod of claim 9, further comprising searching transaction data forrecurring deposits that are not automatic and scraping the recurringdeposits for funder information and storing the funder information incomputer memory.
 13. The method of claim 12, further comprisingretrieving the funder information from computer memory and presentingthe funder information to a user with a suggestion of converting therecurring deposits to automatic deposits made to the second financialinstitution.
 14. The method of claim 13, further comprising determininga recurrence threshold based in time between deposits from the samefunder.
 15. The method of claim 13, further comprising determining arecurrence threshold based on number of times funder is representedwithin the transaction data.
 16. The method of claim 9, wherein therequest from the user comprises login information for granting access toauto deposit controls.
 17. A system for migrating automatic financialservices from a first financial institution to a second financialinstitution over a network of computers comprising computing hardwareand software wherein the software comprises computer readableinstructions that cause the computing hardware to: receive request froma user for migrating current automatic bill payments from a firstfinancial institution to a second financial institution; receive arequest from a user for aggregated account data; retrieve from anaggregation source the desired aggregated account data comprisingtransaction data; determine automatic payments currently being made bythe first financial institution; scrape payment information for each ofthe automatic payments currently being made by the first financially andstoring the payee information in computer memory; scrape payeeinformation for each of the automatic payments currently being made bythe first financially and storing the payee information in computermemory; retrieve new automatic payment forms from the second financialinstitution and populating the new automatic payment forms with thepayee and payment information retrieved from computer memory; and cancelthe current automatic payments with the first financial institution. 18.The system of claim 17, further comprising: reformat the request to becompatible with the aggregation source; send the reformatted request tothe aggregation source over the network of computers; receive requesteddata from the aggregation source over the network of computers; andpresent the aggregated account data to the user.
 19. The system of claim17, further comprising: determine if the payment amount is static andstoring the payment amount in computer memory.
 20. The system of claim17, further comprising: search transaction data for recurring paymentsthat are not automatic and scraping the recurring payments for payeeinformation and storing the payee information in computer memory. 21.The system of claim 20, further comprising: retrieve the payeeinformation from computer memory and presenting the payee information toa user with a suggestion of converting the recurring payments toautomatic payments made by the second financial institution.
 22. Thesystem of claim 21, further comprising: determine a recurrence thresholdbased in time between payments to the same payee.
 23. The system ofclaim 21, further comprising: determine a recurrence threshold based onnumber of times payee is represented within the transaction data. 24.The system of claim 17, wherein the request from the user compriseslogin information for granting access to auto payment controls.